Description

The subgraph-specific interaction mechanics for the guided-tour framework, layered on the framework stack (#2348 / #2299 / #2347 / #2340). Foundation for the Subgraphs tour (#2366) — this PR adds the interaction types and the bridge logic that detects them; the tour content lands in #2366.

Five new tour interactions cover navigating and authoring subgraphs, plus a canvas re-measurement fix so spotlights track the viewport when navigation changes the view.

What changed

Interaction vocabulary (src/components/Learn/tours/registry.ts)

Five new TourStep.interaction values, plus a targetMinCount field:

• navigate-into-subgraph — descends a level (optionally gated to a specific targetTaskName)
• navigate-to-root — returns to the top level
• unpack-subgraph — the active spec's subgraph-task count drops (a subgraph was flattened)
• multi-select-tasks — ≥ targetMinCount (default 2) task nodes are selected
• create-subgraph — the subgraph-task count rises (a subgraph was created)

Bridge handlers (src/routes/v2/pages/Editor/components/EditorTourBridge.tsx)

Each interaction is detected by observing the existing MobX stores — navigation.navigationDepth / navigationPath for level changes, navigation.activeSpec.tasks (counting subgraphSpec) for unpack/create, and editor.multiSelection for multi-select. Following the model from #2299, a detected interaction marks the step complete in the shared tour-progress state (it does not advance the tour itself); already-satisfied-on-entry states are marked complete immediately. Gated "Next" / auto-advance (#2340) handle progression.

Contextual checklist labels

Adds the checklist copy for these interactions (using the contextual bold-target support from #2340):

• navigate-into-subgraph → "Open the {targetTaskName} subgraph"
• multi-select-tasks → "Select {targetMinCount} tasks"
• navigate-to-root → "Return to the top level"
• unpack-subgraph → "Unpack the subgraph"
• create-subgraph → "Create a subgraph from the selected tasks"

Spotlight re-measurement while navigating

• Dispatches a resize event (via requestAnimationFrame) whenever the xyflow viewport pans/zooms during an open tour, so reactour re-positions the highlight/popover after navigating into a subgraph shifts the canvas.
• ensureWindowRestored now waits for the target DOM to actually appear — the step's own selector, else the dock window — polling up to 1.5s before forcing a re-measure, instead of measuring against a not-yet-rendered target.

Related Issue and Pull requests

Progresses https://github.com/Shopify/oasis-frontend/issues/583

Builds on the framework stack (#2348 / #2299 / #2347 / #2340); consumed by the Subgraphs tour in #2366.

Type of Change

• New feature

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

The registry is otherwise inert in this PR — the interactions are exercised end-to-end by the Subgraphs tour in #2366. To verify in isolation:

• No regressions in the existing tours ("Find your way around the editor", "Build your first pipeline"): interaction completion, ensureWindowRestored steps, and the dock/window highlight steps still work.
• Re-measurement — in any canvas-anchored tour step, pan/zoom the viewport; the spotlight/popover should re-position to follow rather than freeze.

Additional Comments

Selector/anchor additions and the seed pipeline for the subgraph tour live in #2366, following the convention that tour-specific DOM anchors ship alongside the tour that needs them.